Skip to content

One single approach to using SHA*. Fixes #3673.#3679

Merged
siegfriedpammer merged 5 commits intomasterfrom
issue3673
Mar 19, 2026
Merged

One single approach to using SHA*. Fixes #3673.#3679
siegfriedpammer merged 5 commits intomasterfrom
issue3673

Conversation

@christophwille
Copy link
Copy Markdown
Member

@christophwille christophwille commented Mar 17, 2026

Additionally, now caches the token for repeating calls.


private byte[]? ComputePublicKeyToken()
{
if (entry.PublicKeyOrToken.IsNil)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is now dead code?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we even bother with caching the result?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GetPublicKeyToken was implemented as a method in order to signal "this might be slow" as opposed to a property where the expectation is O(1).

@siegfriedpammer
Copy link
Copy Markdown
Member

I think the fix of the bug is just local SHA1.Create() + using, no need to bother with caching/lazy init...

@siegfriedpammer siegfriedpammer merged commit 5eebf14 into master Mar 19, 2026
9 checks passed
@christophwille christophwille deleted the issue3673 branch March 20, 2026 07:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants